Skip to content

chore(automation-client): add searchExecutions with cursor pagination - #423

Closed
Seejey01 wants to merge 1 commit into
mainfrom
claude/automation-client-search-executions
Closed

chore(automation-client): add searchExecutions with cursor pagination#423
Seejey01 wants to merge 1 commit into
mainfrom
claude/automation-client-search-executions

Conversation

@Seejey01

@Seejey01 Seejey01 commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Summary

Updates @epilot/automation-client with the new POST /v1/automation/executions:search endpoint (operationId searchExecutions) added in automation-api!368 — cursor-based pagination for an entity's automation executions.

  • src/openapi.json / src/openapi-runtime.json regenerated via npm run openapi <local spec> (the API change is not deployed to prod yet, hence the local spec)
  • src/openapi.d.ts regenerated via npm run typegen; build verified
  • New request/response schemas: SearchExecutionsReq (entity_id, include_flows, size 1–100 default 25, cursor), SearchExecutionsResp (total, results, next_cursor?)
  • Version bumped 2.33.4 → 2.34.0 (minor, new operation) + changeset

Context

GET /v1/automation/executions returns an entity's entire execution history in one response; large histories exceeded Lambda's 6MB response limit (prod Datadog alert 2026-08-04). The new dedicated endpoint paginates instead; the legacy endpoint is unchanged.

Consumers

epilot360-automation-capability (MR!122) will consume client.searchExecutions(...) from this release.

⚠️ Merge order: deploy automation-api!368 first (or at least before UI adoption), then release this client, then bump the UI.


Generated by Claude Code

Update the automation client spec with the new
POST /v1/automation/executions:search endpoint (cursor-based pagination
of an entity's executions) and bump to 2.34.0.

Co-authored-by: Claude <noreply@anthropic.com>
@Seejey01 Seejey01 closed this Aug 5, 2026
@Seejey01
Seejey01 deleted the claude/automation-client-search-executions branch August 5, 2026 09:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants